ClamAV can be used in a few different ways. Most importantly, it provides the ability to scan files in realtime (on-access) or to scan the file system periodically.
I tried configuring ClamAV to both perform on-access virus scanning and to perform nightly full filesystem scanning. Using the on-access option did not prove to be very useful, however a scheduled full system scan seems to be of value.
Here is my story.
| name | wiki |
|---|---|
| description | Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand. |
| argument-hint | ingest | absorb [date-range] | query <question> | cleanup | breakdown | status |
You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| unbind C-b | |
| set-option -g prefix C-a | |
| bind-key C-a send-prefix | |
| # pi coding agent | |
| set -g extended-keys on | |
| set -g extended-keys-format csi-u | |
| # Misc configurations | |
| # Use a stable terminal type rather than inheriting $TERM at server-start time |
| #!/usr/bin/env bun | |
| import { execSync } from 'child_process'; | |
| import { existsSync, statSync } from 'fs'; | |
| import { basename } from 'path'; | |
| interface StatusInput { | |
| session_id: string; | |
| transcript_path: string; | |
| cwd: string; |
Side-by-side comparison of the best AI coding subscriptions: Claude Code, GLM, MiniMax, Kimi, and Qwen
🔗 Full comparison: https://codingplan.org/en
Companion: OmniScape — Art Direction — intent blocks, recipes, value tables, control glossary
Unreal Engine 5.5 or newer · OmniScape on Fab · Demo video
You can use ssacli (smart storage administrator command line interface) tool to manage any of supported HP Smart Array Controllers in your Proxmox host without need to reboot your server to access Smart Storage Administrator in BIOS. That means no host downtime when managing your storage.
CLI is not as convenient as GUI interface provided by BIOS or desktop utilities, but still allows you to fully manage your controller, physical disks and logical drives on the fly with no Proxmox host downtime.
ssacli replaces older hpssacli, but shares the same syntax and adds support for newer servers and controllers.
🔗 Short link to this gist: timw.info/copilotreview
🎥 Associated YouTube video: timw.info/8dc